fix: prevent conflicting required options in design issue template#381
Open
successbyte wants to merge 1 commit intoasyncapi:masterfrom
Open
fix: prevent conflicting required options in design issue template#381successbyte wants to merge 1 commit intoasyncapi:masterfrom
successbyte wants to merge 1 commit intoasyncapi:masterfrom
Conversation
There was a problem hiding this comment.
Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Fixes an issue in the Design Issue Report template where users were forced to select both “Yes” and “No” when indicating whether they want to help fix the issue. This was caused by mutually exclusive checkboxes being marked as required and a duplicate label definition.
Closes #380
Changes
labeldefinitionResult
The issue form no longer blocks submission and provides a clearer contributor experience.
Related issue(s)